Format of a multi-row survey file
The example below shows a multi-row record file.
Notes: Multi-row survey data files are usually created by Visum. Thus, you may read the data from file and store them again multiple times consecutively which means an iterative plausibilization process. Visum creates multi-row survey data record files this way:
To be able to reload survey data of PuT path leg lists that consist of multiple rows, select the format suitable for databases (without header) when you save the attribute file. |
$VISION
* Visum
* 10.11.16
*
*
* Table: Version block
$VERSION:VERSNR;FILETYPE;LANGUAGE;UNIT
10.00;Att;ENG;KM
*
*
* Table: PuT path legs
$PUTPATHLEG:ORIGZONENO;DESTZONENO;PATHINDEX;PATHLEGINDEX;ODTRIPS;DATASETNO;DATASETTYPE;FROMSTOPNO;TOSTOPNO
TSYSCODE;LINENAME;DIRECTIONCODE;LINEROUTENAME;TIMEPROFILENAME;STARTTIMEPROFILEITEMINDEX;ENDTIMEPROFILEITEMINDEX
TYPESTRING;INPUTSTOPDEPDAY;INPUTSTOPDEPTIME;INPUTSTOPNO;DEPDAY
DEPTIME;ARRDAY;ARRTIME
439;110;2;100.000;1;0;;;BUS;B28;>;01;01;4;5;<-V2;;;;1;06:41:00;06:50:00
439;110;4;100.000;1;0;439;54;TRAM;T4;<;02;02;4;6;V1;1;07:00:00;54;1;07:03:00;07:08:00
439;110;6;100.000;1;0;54;14;TRAM;T4;<;02;02;6;9;E;1;07:10:00;54;1;07:08:00;07:13:00
439;110;8;100.000;1;0;14;414;BUS;B26;>;01;01;11;13;N1;1;07:20:00;54;1;07:19:33;07:21:33
The following combinations of input attributes can serve as keys in the file. Then they are mandatory attributes:
- FromStopNo, ToStopNo, InputStopNo and InputStopDepDay / InputStopDepDate and InputStopDepTime
- SurveyVehJourneyNo, FromStopNo, ToStopNo, InputStopNo, InputStopDepDay / InputStopDepDate and InputStopDepTime.
When employing this combination, Visum checks whether a vehicle journey item of the specified vehicle journey exists, which departs at the specified stop in the specified combination of time and day. This vehicle journey item is used as survey path leg from the BoardStopNo to the AlightStopNo if the vehicle journey serves this stop.
- SurveyVehJourneyNo, BoardVehJourneyItemIndex, AlightVehJourneyItemIndex and InputStopDepDay / InputStopDepDate
The survey path leg is identified. A vehicle journey is required which departs at the BoardVehJourneyItemIndex on the same day. If no suitable departure exists, the survey path leg is not plausible.
- SurveyVehJourneyNo, BoardVehJourneyItemIndex and InputStopDepDay / InputStopDepDate
Similar to the key described above. The item following the BoardVehJourneyItemIndex is considered the end of the path leg.
The following table describes the input attributes of a multi-row survey data record file.
Attribute |
Description |
DataSetNo |
Number of the data record |
DataSetType |
Type of the data record {1..32000}, serves as filter criterion for plausibilization (default value: 0) |
InputStopDepDay |
Day of departure of the survey line from the stop specified as InputStopNo. |
InputStopDepTime |
Time of departure of the survey line from the stop specified as InputStopNo. |
InputStopDepDate |
Day of departure of the survey line from the stop specified under InputStopNo. If this attribute is available, it is converted into a calendar day index value according to the calendar used and entered into the attribute InputStopDepDay. |
InputStopNo |
Number of the stop to which InputStopDep and InputStopDepTime and InputStopDepDay refer. |
TimeProfileName |
Name of the time profile |
LineName |
Line name *(mandatory for survey path leg, else optional) |
LineRouteName |
Name of the line route |
ToStopNo |
Number of the ToStop |
ODTrips |
Path volume in [person trips] |
OrigZoneNo |
Number of the origin zone |
DirectionCode |
Direction code |
TypeString |
Type of the path leg, serves for path leg identification (optional)
Note
|
PathLegIndex |
Path leg index |
FromStopNo |
Number of the FromStop |
TSysCode |
Transport system code |
PathInd |
Path index |
DestZoneNo |
Number of the destination zone |
Path\ExtProjFactor |
The external projection factor is a path attribute and must be specified in each row of a data record. If there are different entries, the last value read is adopted. |